Testing Report (Spirits)
Revision History:
| Date |
Author |
Description |
| May. 30 |
Weibin CHENG |
5.30 Integration Test Result |
| Apr. 30 |
Weibin CHENG |
4.30 Unit Test Result |
| Apr. 26 |
Weibin CHENG |
Revision |
| Apr. 24 |
Weibin CHENG |
Test Case(v0.2)&Plan&Progress |
| Apr. 22 |
Weibin CHENG |
Test case(ver. 0.1) |
| Apr 20 |
Ciel ZHAO |
converted the template |
|
|
|
|
|
|
|
|
|
|
|
|
Introduction
Intended Audience and Purpose
This document provides the testing method and results, corresponding to the requirement from the customer. It consists of 3 parts, the testing cases, the test plan, and the testing results.
How to use the document
You may refer to the content section for the structure of the document, in which Sec. Testing Cases collect the unit and module test information from each team; Sec. Testing Plan shows the steps and expected results of the integration test; Sec. Results describes the real world data out of the test, and the correspondence to the requirements.
Test Case
Spirits
All test case below require a stable network connection in general
GUI
- Webpage Openability
(1) Prerequisite
None
(2) Test Steps
a. Open (every) webpage [ckpt 1]
(3) Expected Result
a. The webpage can be opened in 1s[ckpt 1]
- Dimension Adaptability
(1) Prerequisite
None
(2) Test Steps
a. Open (every) webpage [ckpt 1]
b. Resize the browser[ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s[ckpt 1]
b. The layout of the webpage adjust rationally to make the webpage looks normal under different dimension. [ckpt 2 ]
- Buttons&Hyperlinks Work as Expected
(1) Prerequisite
None
(2) Test Steps
a. Open webpage [ckpt 1]
b. Click buttons&hyperlinks[ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s[ckpt 1]
b. Buttons and hyperlinks work as expected, i.e. buttons work normally/link to correct subpages[ckpt 2]
Admin Privileges
- Admin log in—Normal
(1) Prerequisite
None
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input login info [ckpt 2]
c. Login [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The login info can be input normally [ckpt 2]
c. The webpage redirect(200 succ.) or prompt wrong/mismatched usrname&passwd according to server response(403/Timeout: failed) [ckpt 3]
- Admin log in—Empty UserName
(1) Prerequisite
None
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input password but leaves username to be empty[ckpt 2]
c. Try to log in
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The login info can be input normally [ckpt 2]
c. The login button is locked since empty username is not permitted, and prompt info is shown [ckpt 3]
- Admin log in—Empty Password
(1) Prerequisite
None
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input username but leave password to be empty[ckpt 2]
c. Try to log in
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The login info can be input normally [ckpt 2]
c. The login button is locked since empty password is not permitted, and prompt info is shown [ckpt 3]
- Admin log out
(1) Prerequisite
None
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Logout [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage redirect and prompt logout succeful(200 succ.) or do nothing(Timeout: failed) [ckpt 2]
- Admin downloads the calibration data from the cloud—Normal
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input device uuid [ckpt 2]
c. Download calibration data [ckpt 3]
d. Check if the calibration data is downloaded successfully [ckpt 4]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The uuid can be input normally, and uuid format is checked, if is invalid then download button is locked [ckpt 2]
c. The webpage prompts the user download starts [ckpt 3]
d. The calibration data is downloaded. [ckpt 4]
- Admin downloads the calibration data from the cloud—Exception(no calibration data(404), server respond timeout, network broke halfway, e.t.c.)
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input device uuid [ckpt 2]
c. Download calibration data [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The uuid can be input normally, and uuid format is checked, if it’s invalid then download button is locked [ckpt 2]
b. The webpage prompts user error according to server response[ckpt 3]
- Admin uploads a new model to the cloud—Normal
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input device uuid [ckpt 2]
c. Upload calibration data [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The uuid can be input normally, and uuid format is checked, if it’s invalid then upload button is locked [ckpt 2]
c. The webpage prompts the user upload starts [ckpt 3]
- Admin uploads a new model to the cloud—Exception(server respond timeout, network broke halfway, e.t.c.)
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input device uuid [ckpt 2]
c. Upload calibration data [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The uuid can be input normally, and uuid format is checked, if it’s invalid then upload button is locked [ckpt 2]
c. The webpage prompts the user error [ckpt 3]
- Admin clear/ban a device
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Input device uuid [ckpt 2]
c. Click ban/clear button [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The uuid can be input normally, and uuid format is checked, if it’s invalid then upload button is locked [ckpt 2]
c. The webpage prompts the user operation status (200 succ, no resp. failed).[ckpt 3]
- Admin upload&set base model—Normal
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Selete and upload model [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. Model can be seletd and is uploaded to server. The webpage prompts successful operation(200:succ.) [ckpt 2]
- Admin upload&set base model—Exception(server respond timeout, network broke halfway, e.t.c.)
(1) Prerequisite
a. The admin is logged in
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Select and upload a model [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. Model can be seletd and is uploaded to server. The webpage prompts error. [ckpt 2]
User Cloud Operation
- User sets the contact email—Correct email
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Inputs email of correct format [ckpt 2]
c. Submit [ckpt 3]
d. Check if email is set successfully [ckpt 4]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The email can be input normally [ckpt 2]
c. The submit button can be clicked normally [ckpt 3]
d. The webpage prompts the user success [ckpt 4]
(4) Sample Test Data
a. sample123@qq.com
b. sample55@163.com
c. sample@jlu.edu.cn
d. sample@sample.net
- User sets the contact email—Email of wrong format
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
b. Inputs email of wrong format [ckpt 2]
(2) Expected Result
a. The webpage opens in 1s normaly [ckpt 1]
b. The email can be input normally, but the webpage prompts the user wrong email format and locks the submit button [ckpt 2]
(3) Sample Test Data
a. sdfsadf
b. -+23.-0512
c. www.baidu.com
d. @@@@@
- User sets the contact email—Too long email
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
b. Inputs extremely long email(length>254) [ckpt 2]
(2) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. Only the first 254 characters can be inputed. [ckpt 2]
(3) Sample Test Data
a. c…c(c*255)
- User sets the contact email—Other exception(Server returns 400)
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
b. Inputs email of correct format [ckpt 2]
c. Submit [ckpt 3]
d. Check set status [ckpt4]
(2) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The email can be input normally [ckpt 2]
c. The submit button can be clicked normally[ckpt 3]
d. The webpage prompts the user setting failure. [ckpt4]
(3) Sample Test Data
a. sample123@qq.com
b. sample55@163.com
c. sample@jlu.edu.cn
d. sample@sample.net
- User inspects the contact email—Email was set already
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
(2) Expected Result
a. The webpage is opened in 1s normally and shows the set email [ckpt 1]
- User inspects the contact email—Email was not set yet
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
(2) Expected Result
a. The webpage is opened in 1s normally but prompts user unset email [ckpt 1]
- User deletes email setting—Email was set already
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
b. Deletes email setting [ckpt 2]
(2) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The email setting is deleted successfully and the webpage prompts user successful operation. [ckpt 2]
- User deletes email setting—Email was not set yet
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
(2) Expected Result
a. The webpage is opened in 1s normally but the ‘delete’ button is locked [ckpt 1]
- User checks calibration data availability on the server
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
(3) Expected Result
a. The webpage is opened in 1s normally and shows if the calibration data is available on server currently according to server response(404 no, 200 yes) [ckpt 1]
- User uploads new calibration data to the cloud —Normal
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Upload data [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts user successful operation[ckpt 2]
- User uploads new calibration data to the cloud—Exception(invalid signature, no calibration data, server respond timeout, network broke halfway, e.t.c.)
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Upload the data [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts the user error according to server response(400(cloud side): invalid signature, 404(device side):no calibration data, Timeout: upload failed)[ckpt 2]
- User clears calibration data from the cloud
(1) Prerequisite
a. The device is connected and activated already
(1) Test Steps
a. Open related webpage [ckpt 1]
b. Clears the email setting [ckpt 2]
(2) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The calibration data is deleted successfully and the webpage prompts user successful operation. [ckpt 2]
- User checks the version of the device model on the server
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage and check the version [ckpt 1]
b.
(3) Expected Result
a. The webpage is opened in 1s normally and shows the current model version according to server response.[ckpt 1]
- User downloads the newest model from server—Normal
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Downloads the model [ckpt 2]
c. Check if the model is downloaded successfully [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts user download starts.[ckpt 2]
c. The model is downloaded successfully [ckpt 3]
- User downloads the newest model from server—Exception(server respond timeout, network broke halfway, e.t.c.)
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Downloads the model [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts the user error.[ckpt 2]
- User resets model version—Normal
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Resets the model [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts user reset succeeded [ckpt 2]
- User resets model version—Exception(server respond timeout, network broke halfway, e.t.c.)
(1) Prerequisite
a. The device is connected and activated already
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Resets the model [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts the user error.[ckpt 2]
User Local Operation
- User connects the device
(1) Prerequisite
None
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Selects and connects a device [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts user connecting result(200:succ, timeout:failed) [ckpt 2]
- User gets and inspects status information of the device
(1) Prerequisite
a. The device is connected and activated
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Gets status information [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage shows the information gotten [ckpt 2]
- User download the model from the device—Normal
(1) Prerequisite
a. The device is connected and activated
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Downloads the model from the device [ckpt 2]
c. Check if the model is downloaded successfully [ckpt 3]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage shows download starts [ckpt 2]
c. The model is downloaded successfully [ckpt 3]
- User download the model from the device—Excetion(No model currently(404), server respond timeout, e.t.c.)
(1) Prerequisite
a. The device is connected and activated
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Downloads the model from the device [ckpt 2]
(3) Expected Result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompts error(404:no model, Timeout:operation failed) [ckpt 2]
- User starts to calibrate
(1) Prerequisite
a. The device is connected and activated
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Starts to calibrate [ckpt 2]
c. Finish calibrate [ckpt 3]
(3) Expected result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage shows calibration guide according to server response [ckpt 2]
c. The webpage prompts users calibrating finished [ckpt 3]
- User deletes local calibration data
(1) Prerequisite
a. The device is connected and activated
(2) Test Steps
a. Open related webpage [ckpt 1]
b. Clears local calibration data. [ckpt 2]
(3) Expected result
a. The webpage is opened in 1s normally [ckpt 1]
b. The webpage prompt user operation status according to server response(200:succ, timeout:failed) [ckpt 2]
Test Plan
Introduction
Purpose
The test plan introduces how to test the interaction module of the system, which provides testing range, testing strategy and personnel arrangement, e.t.c.
Background
The interaction module is responsible for the interaction with users, the display of information, and system management by administrator.
Features to Be Tested
Features below are planned to be tested to ensure the interaction module of the system meets the specified requirements
- Administrator Privileges
- Login and Logout
- Model Management
Upload new model
Set base model
Reset model
- Device Management
Clear data coresponding to a specified device
Ban a device
Download calibration data of a specified device
- User Cloud Operation
- User Identification
Set email
Inspect current email setting
Delete current email setting
- Calibration-related
Update new calibration data
Check calibration data availability on the cloud
Clear calibration data on the cloud
- Model-related
Check current model version
Download the newest model from cloud
Reset model version
- User Device Operation
- Connectivity
Connect to the device
- Calibration-related
Start to calibrate
Clear local calibration data
- Data Exchange
Get device status information
Download the model from the device
Upload a new model to the device
- GUI
- User-friendly
Good appearance
Rational layout design
Clear button/link/… naming
Acceptable response time
- Compatibility
Resposive Design
Cross-platform
- Error Handling
Factors not considered currently
In current stage, we assume there is a relatively stable network connection while using the system. Therefore, network failure is ignored.
Besides, we do not consider safety issues
…
Test Reference and Submission Documentation
Test Reference Documentation
- System Requirement Specification
- System Design Specification
- Interface Specification
Test Submission Documentation
- Test Plan
- Test Case
- Test Report
- Current Bugs
Test Timeline
| Test Activity |
Expected Start Data |
Actual Start Date |
Duration/Day(s) |
| Making test plans |
4.22 |
4.22 |
2 |
| Unit Test |
4.26 |
4.26 |
1-3 |
| Integration Test |
5.30 |
|
2-3 |
| Validation Test |
5.4 |
|
|
Test Resource
Personnel
Weibin CHENG
Environment
Windows 11
Google Chrome Version 100.0.4896.127 (Official Build) (64-bit)
…(e.t.c)
Test Results(Based on Requirement Analysis)
End User
Connect App to Device
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Device webpage(device activated or uuid is designated) |
Buttons requiring uuid are unlocked and device info(email) is shown |
As expected |
|
| Enter Device webpage(with unactivated device and no uuid designated) |
Buttons requiring uuid are locked |
As expected |
|
| Activate Device |
Activate Successfully. Display device info, e.t.c. |
As expected |
|
See Device Status
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Device webpage(device activated or uuid is designated) |
Buttons requiring uuid are unlocked and device info(email) is shown |
As expected |
|
| Enter Device webpage(with unactivated device and no uuid designated) |
Buttons requiring uuid are locked |
As expected |
|
| See Device Status |
The status of current device is shown |
As expected |
|
| Get email(valid uuid) |
Email binded on the device is shown |
As expected |
|
| Get email(invalid uuid) |
prompts error info and refresh the webpage |
As expected |
|
Calibrate Device
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter calibration webpage(device activated or uuid designated) |
Buttons are shown |
As expected |
|
| Enter calibration webpage(uuid empty) |
Buttons are hidden |
As expected |
|
| Start calibration |
Calibration starts successfully |
As expected |
|
| Interupt calibration |
The webpage refreshes and reset to origin |
As expected |
|
Choose Algorithm to train
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter model webpage(device acitaved or valid uuid designated) |
Buttons are shown |
As expected |
|
| Enter model webpage(unacitaved and no uuid designated) |
Buttons are hidden |
As expected |
|
| Train model(device activated or correct uuid designated) |
Trainning starts successfully |
As expected |
|
| Train model(invalid uuid is designated) |
Prompts error |
As expected |
|
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Device webpage(device activated or uuid is designated) |
Buttons requiring uuid are unlocked and device info(email) is shown |
As expected |
|
| Enter Device webpage(with unactivated device and no uuid designated) |
Buttons requiring uuid are locked |
As expected |
|
| Set Email |
Email changed successfully and new email is displayed in the GUI |
As expected |
|
Download Model for Chosen Algorithm
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter model webpage(device acitaved or valid uuid designated) |
Buttons are shown |
As expected |
|
| Enter model webpage(unacitaved and no uuid designated) |
Buttons are hidden |
As expected |
|
| Choose a model |
Model is chosen and its introduction is shown |
As expected |
|
| Download base model from cloud(valid uuid) |
Base model is downloaded from cloud |
As expected |
|
| Download base model from cloud(invalid uuid) |
Prompts err info |
As expected |
|
| Synchronize model(valid uuid) |
Prompts user of operation success |
As expected |
|
| Synchronize model(invalid uuid) |
Prompts user of failure |
As expected |
|
Clear(Part of) Data from Cloud
| Test Case |
Expected Result |
Actual Result |
Remark |
| Clear calibration data on cloud |
Prompt user of success |
As expected |
|
| Delete device model |
Prompts user of operation success |
As expected |
|
| Unbind Email |
Email cleared successfully and Null Email is displayed |
As expected |
|
Reset Device
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Device webpage(device activated or uuid is designated) |
Buttons requiring uuid are unlocked and device info(email) is shown |
As expected |
|
| Enter Device webpage(with unactivated device and no uuid designated) |
Buttons requiring uuid are locked |
As expected |
|
| Reset device |
All information of current device on the cloud is deleted |
As Expected |
|
Power Off Device
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Device webpage(device activated or uuid is designated) |
Buttons requiring uuid are unlocked and device info(email) is shown |
As expected |
|
| Enter Device webpage(with unactivated device and no uuid designated) |
Buttons requiring uuid are locked |
As expected |
|
| Deactivate Device |
Deactivate Successfully. Lock relevant buttons, e.t.c. |
As expected |
|
Enterprise
Set up Cloud & Produce Device
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Device webpage(device activated or uuid is designated) |
Buttons requiring uuid are unlocked and device info(email) is shown |
As expected |
|
| Enter Device webpage(with unactivated device and no uuid designated) |
Buttons requiring uuid are locked |
As expected |
|
| Designate uuid(device webpage) |
Buttons hidden/locked while changing uuid, after confirm, uuid change as input content successfully, and uuid relevant info is shown |
As expected |
|
| Designate uuid(algorithm webpage) |
Buttons hidden while changing uuid, after confirm, uuid change as input content successfully, and uuid relevant info is shown |
As expected |
|
Login
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter Login webpage |
The webpage finishes loading in 1s |
As expected |
|
| Admin Login(correct user name and password) |
Login successfully and prompts user of success |
As expected |
|
| Admin Login(wrong or unmatch user name and password) |
Login failed and prompts user of success failure |
As expected |
|
Download Calibration Data of Device from Cloud
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter calibration webpage(device activated or uuid designated) |
Buttons are shown |
As expected |
|
| Enter calibration webpage(uuid empty) |
Buttons are hidden |
As expected |
|
| download calibration data from cloud(valid uuid) |
Download successfully |
As expected |
|
| download calibration data from cloud(invalid uuid) |
Prompt user of failure |
As expected |
|
Download Model from Device
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter model webpage(device acitaved or valid uuid designated) |
Buttons are shown |
As expected |
|
| Enter model webpage(unacitaved and no uuid designated) |
Buttons are hidden |
As expected |
|
| Download device model |
Prompts user of operation success |
As expected |
|
Upload Model for Device on Cloud
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter model webpage(device acitaved or valid uuid designated) |
Buttons are shown |
As expected |
|
| Enter model webpage(unacitaved and no uuid designated) |
Buttons are hidden |
As expected |
|
| Upload device model |
Prompts user of success |
As expected |
|
Upload Base Model for Algorithms on Cloud
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter model webpage(device acitaved or valid uuid designated) |
Buttons are shown |
As expected |
|
| Enter model webpage(unacitaved and no uuid designated) |
Buttons are hidden |
As expected |
|
| Upload base model on the cloud(Wrong file format) |
Prompts user of error |
As expected |
|
| Upload base model on the cloud(Correct) |
Prompts user of success |
As expected |
|
Delete Cloud Model
| Test Case |
Expected Result |
Actual Result |
Remark |
| Enter model webpage(device acitaved or valid uuid designated) |
Buttons are shown |
As expected |
|
| Enter model webpage(unacitaved and no uuid designated) |
Buttons are hidden |
As expected |
|
| Reset cloud model to base(valid uuid) |
Operation successfully done and prompts user of success |
As expected |
|
| Reset cloud model to base(invalid uuid) |
Prompts user of error |
As expected |
|
| Delete all model on the cloud(valid uuid) |
Operation successfully completed and prompts user of success |
As expected |
|
| Delete all model on the cloud(invalid uuid) |
Operation failed and prompts user of failure |
As expected |
|